File system adapted for use with a dispersed data storage network

ABSTRACT

A file system interface to a dispersed data storage network is disclosed. The disclosed interface accepts read and write commands from a file system resident on a user&#39;s computer and generates network commands that are forwarded to slice servers that form the storage component of the dispersed data storage network. The slice servers then fulfill the read and write commands.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent application Ser. No. 11/973,613, entitled “BLOCK BASED ACCESS TO A DISPERSED DATA STORAGE NETWORK,” filed Oct. 9, 2007, assigned to Cleversafe, Inc. of Chicago, Ill., and which is hereby incorporated by reference in its entirety.

REFERENCE TO INCORPORATED COMPACT DISC

This application incorporates by reference the following source code files submitted on a compact disc along with this application:

Directory of D:\ 07/03/2008 05:12 PM 4,033 ABSOLUTE.JAV 07/01/2008 09:23 AM 9,693 CACHEDD2.JAV 07/02/2008 04:34 PM 4,255 CACHEDDI.JAV 07/10/2008 11:05 AM <DIR> DIRECTOR 06/30/2008 03:04 PM 1,522 DISPERS2.JAV 06/30/2008 03:27 PM 2,689 DISPERS3.JAV 06/04/2008 06:03 PM 2,728 DISPERS4.JAV 07/03/2008 04:06 PM 19,034 DISPERS5.JAV 06/26/2008 05:29 PM 10,222 DISPERS6.JAV 07/03/2008 05:12 PM 4,710 DISPERS7.JAV 06/30/2008 03:04 PM 8,269 DISPERSE.JAV 07/01/2008 09:23 AM 30,312 EDITABL2.JAV 06/30/2008 03:27 PM 15,241 EDITABL3.JAV 06/11/2008 04:53 PM 2,235 EDITABL4.JAV 06/27/2008 03:58 PM 3,126 EDITABLE.JAV 07/10/2008 11:05 AM <DIR> EXCEPTIO 07/03/2008 05:12 PM 20,070 FILEDEVI.JAV 06/30/2008 05:15 PM 4,544 FILEVAU2.JAV 06/30/2008 05:15 PM 6,991 FILEVAUL.JAV 06/04/2008 06:03 PM 1,935 METADATA.JAV 07/03/2008 05:12 PM 7,081 PATH.JAV 06/30/2008 03:04 PM 5,559 READONLY.JAV 07/03/2008 05:12 PM 3,900 RELATIVE.JAV 06/17/2008 10:57 AM 2,576 ROOTDIRE.JAV 22 File(s) 170,725 bytes Directory of D:\DIRECTOR 07/10/2008 11:05 AM <DIR> . 07/10/2008 11:19 AM <DIR> .. 06/17/2008 04:42 PM 1,560 DIRECTO2.JAV 06/17/2008 04:42 PM 1,457 DIRECTO3.JAV 06/24/2008 11:53 AM 9,974 DIRECTOR.JAV 07/10/2008 11:05 AM <DIR> EXCEPTIO 06/11/2008 11:20 AM 939 FILETYPE.JAV 07/10/2008 11:05 AM <DIR> XML 4 File(s) 13,930 bytes Directory of D:\DIRECTOR\EXCEPTIO 07/10/2008 11:05 AM <DIR> . 07/10/2008 11:05 AM <DIR> .. 06/17/2008 02:29 PM 1,426 ENTRYALR.JAV 1 File(s) 1,426 bytes Directory of D:\DIRECTOR\XML 07/10/2008 11:05 AM <DIR> . 07/10/2008 11:05 AM <DIR> .. 06/17/2008 04:42 PM 2,667 XMLDIRE2.JAV 06/17/2008 04:42 PM 2,980 XMLDIREC.JAV 2 File(s) 5,647 bytes Directory of D:\EXCEPTIO 07/10/2008 11:05 AM <DIR> . 07/10/2008 11:19 AM <DIR> .. 07/02/2008 02:36 PM 1,805 DIRECTOR.JAV 06/27/2008 09:54 AM 538 FILEDOES.JAV 06/17/2008 04:42 PM 332 FILEEXIS.JAV 06/17/2008 04:42 PM 1,637 FILEREAD.JAV 06/17/2008 02:29 PM 1,784 FILESYS2.JAV 06/17/2008 04:42 PM 546 FILESYST.JAV 06/17/2008 04:42 PM 1,605 FILEWRIT.JAV 06/17/2008 02:29 PM 268 ILLEGALF.JAV 06/17/2008 04:42 PM 1,448 INVALIDF.JAV 07/02/2008 02:36 PM 1,778 ISADIREC.JAV 06/17/2008 04:42 PM 444 METADATA.JAV 07/02/2008 02:36 PM 1,782 NOTADIRE.JAV 07/02/2008 02:36 PM 1,619 UNSUPPOR.JAV 13 File(s) 15,586 bytes Total Files Listed: 42 File(s) 207,314 bytes 12 Dir(s) 0 bytes free

FIELD OF THE INVENTION

The present invention relates generally to systems, apparatus, and methods for distributed data storage, and more particularly to systems, apparatus, and methods for distributed data storage using an information dispersal algorithm so that no one location will store an entire copy of stored data, and more particularly still to systems, apparatus, and methods for reading data from and writing data to a dispersed data storage network.

DESCRIPTION OF THE PRIOR ART

Storing data in digital form is a well-known problem associated with all computer systems, and numerous solutions to this problem are known in the art. The simplest solution involves merely storing digital data in a single location, such as a punch film, hard drive, or FLASH memory device. However, storage of data in a single location is inherently unreliable. The device storing the data can malfunction or be destroyed through natural disasters, such as a flood, or through a malicious act, such as arson. In addition, digital data is generally stored in a usable file, such as a document that can be opened with the appropriate word processing software, or a financial ledger that can be opened with the appropriate spreadsheet software. Storing an entire usable file in a single location is also inherently insecure as a malicious hacker only need compromise that one location to obtain access to the usable file.

To address reliability concerns, digital data is often “backed-up,” i.e., an additional copy of the digital data is made and maintained in a separate physical location. For example, a backup tape of all network drives may be made by a small office and maintained at the home of a trusted employee. When a backup of digital data exists, the destruction of either the original device holding the digital data or the backup will not compromise the digital data. However, the existence of the backup exacerbates the security problem, as a malicious hacker can choose between two locations from which to obtain the digital data. Further, the site where the backup is stored may be far less secure than the original location of the digital data, such as in the case when an employee stores the tape in her home.

Another method used to address reliability and performance concerns is the use of a Redundant Array of Independent Drives (“RAID”). RAID refers to a collection of data storage schemes that divide and replicate data among multiple storage units. Different configurations of RAID provide increased performance, improved reliability, or both increased performance and improved reliability. In certain configurations of RAID, when digital data is stored, it is split into multiple stripes, each of which is stored on a separate drive. Data striping is performed in an algorithmically certain way so that the data can be reconstructed. While certain RAID configurations can improve reliability, RAID does nothing to address security concerns associated with digital data storage.

One method that prior art solutions have addressed security concerns is through the use of encryption. Encrypted data is mathematically coded so that only users with access to a certain key can decrypt and use the data. Common forms of encryption include DES, AES, RSA, and others. While modern encryption methods are difficult to break, numerous instances of successful attacks are known, some of which have resulted in valuable data being compromised.

Files are usually organized in file systems, which are software components usually associated with an operating system. Typically, a file system provides means for creating, updating, maintaining, and hierarchically organizing digital data. A file system accepts digital data of arbitrary size, segments the digital data into fixed-size blocks, and maintains a record of precisely where on the physical media data is stored and what file the data is associated with. In addition, file systems provide hierarchical directory structures to better organize numerous files.

Various interfaces to storage devices are also well known in the art. For example, Small Computer System Interface (“SCSI”) is a well known family of interfaces for connecting and transferring data between computers and peripherals, including storage. There are also a number of standards for transferring data between computers and storage area networks (“SANs”). For example, Fibre Channel is a networking technology that is primarily used to implement SANs. Fibre Channel SANs can be accessed through SCSI interfaces via Fibre Channel Protocol (“FCP”), which effectively bridges Fibre Channel to higher level protocols within SCSI. Internet Small Computer System Interface (“iSCSI”), which allows the use of the SCSI protocol over IP networks, is an alternative to FCP, and has been used to implement lower cost SANs using Ethernet instead of Fibre Channel as the physical connection. Interfaces for both FCP and iSCSI are available for many different operating systems, and both protocols are widely used. The iSCSI standard is described in “Java iSCSI Initiator,” by Volker Wildi, and Internet Engineering Task Force RFC 3720, both of which are hereby incorporated by reference.

In 1979, two researchers independently developed a method for splitting data among multiple recipients called “secret sharing.” One of the characteristics of secret sharing is that a piece of data may be split among n recipients, but cannot be known unless at least t recipients share their data, where n≧t. For example, a trivial form of secret sharing can be implemented by assigning a single random byte to every recipient but one, who would receive the actual data byte after it had been bitwise exclusive orred with the random bytes. In other words, for a group of four recipients, three of the recipients would be given random bytes, and the fourth would be given a byte calculated by the following formula: s′=s⊕r_(a)⊕r_(b)⊕r_(c), where s is the original source data, r_(a), r_(b), and r_(c) are random bytes given to three of the four recipients, and s′ is the encoded byte given to the fourth recipient. The original byte s can be recovered by bitwise exclusive-orring all four bytes together.

The problem of reconstructing data stored on a digital medium that is subject to damage has also been addressed in the prior art. In particular, Reed-Solomon and Cauchy Reed-Solomon coding are two well-known methods of dividing encoded information into multiple slices so that the original information can be reassembled even if all of the slices are not available. Reed-Solomon coding, Cauchy Reed-Solomon coding, and other data coding techniques are described in “Erasure Codes for Storage Applications,” by Dr. James S. Plank, which is hereby incorporated by reference.

Traditional disk-oriented file systems offer the ability to store and retrieve user-visible files, directories and their metadata. In addition to this data, and transparent to the file system user, is the file system metadata which is comprised of various elements of concern to the file system itself or its immediate execution context of the operating system kernel. File system metadata (often called the superblock in UNIX parlance) is composed of such things as the magic number identifying the file system, vital numbers describing geometry, statistics and behavioral tuning parameters and a pointer to the tree's root. This has various implications, the most crucial of which being that a file system cannot “bootstrap” itself, or bring itself online, if the superblock were to ever become corrupt.

Schemes for implementing dispersed data storage networks (“DDSNs”), which are also known as dispersed data storage grids, are also known in the art. In particular, U.S. Pat. No. 5,485,474, issued to Michael O. Rabin, describes a system for splitting a segment of digital information into n data slices, which are stored in separate devices. When the data segment must be retrieved, only m of the original data slices are required to reconstruct the data segment, where n>m.

In October of 2007, Cleversafe, Inc. of Chicago, Ill. released the first dispersed data storage network to incorporate an iSCSI device interface. This release allowed users of non-specialized computer systems, such as Windows Workstations, Macintosh Workstations, and Linux Workstations, to make use of dispersed data storage network technology. This constituted a significant step forward in providing significant access to dispersed data storage technology. However, subsequent use and testing has revealed that additional improvements could be made in providing better performing and more accessible dispersed data storage technology.

Most importantly, users of Cleversafe's iSCSI interface must rely on a standard file system, such as FAT, NTFS, HFS+, or ext3, to store their files. These file systems were designed to work with localized storage solutions, and accordingly, do not account for the specific requirements of file storage and retrieval on a dispersed data storage network. For example, file systems store not only files, but information about the files called metadata. One type of metadata is used to establish an organization for the files known as a directory structure. Most file systems require that each access must traverse the directory structure from the root node to the particular file to be accessed. With a localized storage solution, the performance impact of such a traverse is minimal.

OBJECTS OF THE INVENTION

Accordingly, it is an object of this invention to provide a system, apparatus, and method for implementing a file system especially adapted for use with a dispersed data storage network.

Another object of the invention is to provide a system, apparatus, and method for implementing a metadata caching file system to provide a better performing file system adapted for use with a dispersed data storage network.

Another object of the invention is to provide a system, apparatus, and method for implementing a variable segment size file system for use with a dispersed data storage network.

Other advantages of the disclosed invention will be clear to a person of ordinary skill in the art. It should be understood, however, that a system, method, or apparatus could practice the disclosed invention while not achieving all of the enumerated advantages, and that the protected invention is defined by the claims.

SUMMARY OF THE INVENTION

The disclosed invention achieves its objectives by providing file based access to a dispersed data storage network. In one embodiment, a method of reading data from a dispersed data storage network is disclosed. In this embodiment, a computer seeking to access the dispersed data storage network requests access to a file object referencing data stored on the dispersed data storage network using a software interface. A metadata object associated with the requested file object is loaded into a file system cache. Using the loaded metadata object the requested file object is then loaded into the file system cache.

In an alternate embodiment, a method of writing data to a dispersed data storage network is disclosed. A program utilizes a software interface and requests the creation of a file object that will be associated with the data to be written to the dispersed data storage network. A directory object that will reference the file object is then identified, and a writeable copy of the directory object is made. A reference to the file object is created within the writeable directory object, and the original directory object is invalidated. The writeable directory object is copied to a new read only directory object, and the contents of the writeable directory object are written to the dispersed data storage network. The writeable directory object is then destroyed.

In another embodiment, a file system object is opened, and a collection of data is written to the file system object. Before dispersal to the dispersed data storage network, the collection of data is segmented into a plurality of varying size data segments, each of which is then sliced and written to a plurality of slice servers. A refinement of this embodiment includes arranging the data segments so that data located near the beginning of a collection of data is written as smaller data segments, while data located near the end of a collection of data is written as larger data segments.

Another embodiment of the disclosed invention is directed to a grid access computer which implements a virtual file system for accessing a dispersed data storage network. The grid access computer comprises a network port for receiving packets from client computers and slice servers operating on the dispersed data storage network. A network layer receives packets from client computers through the network port, and a file object layer issues different packets to slice servers to implement read and/or write operations based on the received packets. In a further refinement of this embodiment, a server layer parses the received packets and based on the received packets issues commands to the file object layer.

BRIEF DESCRIPTION OF THE DRAWINGS

Although the characteristic features of this invention will be particularly pointed out in the claims, the invention itself, and the manner in which it may be made and used, may be better understood by referring to the following description taken in connection with the accompanying drawings forming a part hereof, wherein like reference numerals refer to like parts throughout the several views and in which:

FIG. 1 is a network diagram of a dispersed data storage network constructed in accordance with an embodiment of the disclosed invention;

FIG. 2 is a block diagram illustrating the interoperation of different software components used to implement a dispersed data storage network constructed in accordance with an embodiment of the disclosed invention;

FIG. 3 is a block diagram illustrating the interoperation of different software components used to implement a dispersed data storage network constructed in accordance with a different embodiment of the disclosed invention;

FIGS. 4A-4C collectively illustrate a read operation from a dispersed data storage network constructed in accordance with an embodiment of the disclosed invention;

FIGS. 5A-5B collectively illustrate a write operation from a dispersed data storage network constructed in accordance with an embodiment of the disclosed invention;

FIG. 6 is a block diagram illustrating the interoperation of different software components used to access dispersed data storage network using the disclosed File-Object interface and constructed in accordance with an embodiment of the disclosed invention;

FIG. 7 is a flowchart illustrating at a high level how a file object is loaded by dispersed data storage network constructed in accordance with an embodiment of the disclosed invention;

FIG. 8A is a flowchart illustrating how a directory object is loaded by a dispersed data storage network constructed in accordance with an embodiment of the disclosed invention;

FIG. 8B is a flowchart illustrating how a file object is loaded by a dispersed data storage network constructed in accordance with an embodiment of the disclosed invention;

FIG. 9 is a flowchart illustrating the high level process of creating a file or directory object in accordance with an embodiment of the disclosed invention;

FIG. 10A is a flowchart illustrating the details of creation of a file object in accordance with an embodiment of the disclosed invention;

FIG. 10B is a flowchart illustrating the creation of a directory object in accordance with an embodiment of the disclosed invention;

FIG. 11A is a flowchart illustrating the segmenting of a file or directory object before writing, in accordance with an embodiment of the disclosed invention; and

FIG. 11B is a flowchart illustrating the reconstructing of segmented data during a read, in accordance with an embodiment of the disclosed invention.

DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENT

Turning to the Figures, and to FIG. 1 in particular, a distributed computer system implementing a dispersed data storage network 100 is shown. An arbitrary number of slice servers 150-162 store data slices sent to them by networked source computers 102,104,106. As illustrated, some number of grid access computers 120,122 serve as networked iSCSI Targets for an arbitrary number of source computers 102,104,106, which are configured as iSCSI Initiators.

As explained herein, the disclosed invention allows a dispersed data storage network to be presented as a block device which can be mounted as a network drive by compatible operating systems. As illustrated, the dispersed data storage network is accessed by the source computers 102,104,106, as an iSCSI Target. In particular, each source computer 102,104,106 writes data blocks to an iSCSI Initiator, which forms network commands that are directed to an associated iSCSI Target, which is in this case implemented on grid access computers 120,122. Note that an iSCSI Target could be implemented on the source computers 102,104,106, which would make the grid access computers 120,122 unnecessary. In addition, a different storage protocol, such as FCP or ATA over Ethernet could be used, or a device driver could be implemented directly on the source computers 102,104,106 to present the dispersed data storage network as a mounted drive. The iSCSI implementation discussed herein is only used as a device to aid the understanding of the disclosed invention by a person of ordinary skill in the art.

FIG. 2 illustrates a distributed computer system implementing a dispersed data storage network 200. The illustrated system consists of a client/user computer 202, a grid access computer 220, and some number of slice servers 240,250,260. Within the client computer 202 an application program 204 accesses an operating system including a file system 206. The operating system may include a separate block layer 208, meaning an interface to block devices such as storage device drivers, or the functionality of the block layer 208 may be incorporated into the file system 206. In either case, read and write commands directed to the file system are forwarded to an iSCSI Initiator 210, which formulates network commands that are carried out by a network layer 212, which is also part of the operating system operating on the client computer 202.

As illustrated, the iSCSI Initiator 210 operating on the client computer 202 is configured to operate with iSCSI Target 222, resident on grid access computer 220. The iSCSI Target 222 receives network commands from the iSCSI Initiator 210 via a separate network layer 224 operating on the grid access computer 220. As opposed to a standard iSCSI Target, which would merely store data on one or more drives accessible to the iSCSI Target, the iSCSI Target 222 operating on the grid access computer 220 is configured to operate with a dispersed data storage network. As will be explained in more detail in the sections that follow, the iSCSI Target 222 communicates with DDSN Client Library 221, which implements a data dispersal algorithm in accordance with the commands received from the iSCSI Initiator 210, and either retrieves data from appropriate slice servers 240,250,260 or writes data to the same. Each slice server 240,250,260 also contains a grid server application 244,254,264 that stores and retrieves data slices in accordance with network commands received from the grid access computer 220 via the network layers 242,252,262 of the respective slice servers 240,250,260.

FIG. 3 illustrates a slightly different distributed computer system implementing a dispersed data storage network 300. The illustrated system is identical to that shown in FIG. 2, except that the grid access computer 220 has been entirely removed, and, instead of using an iSCSI Target 222 to implement a block interface to the dispersed data storage network, a device driver 310 resident on the client user computer 302 implements the block interface. In this implementation, the device driver 310 receives read and write commands from the file system 206. The device driver 310 is configured to fulfill read and write commands through the dispersed data storage network 240,250,260. Like the iSCSI Target 222 of the previously discussed implementation, the device driver 310 implements a data dispersal algorithm in accordance with the commands received from the file system 206, and either retrieves data from appropriate slice servers 240,250,260 or writes data to the same. The embodiment of FIG. 3 is otherwise similar to that of FIG. 2.

FIGS. 4A-4C show the process by which an iSCSI Target, or other data dispersal/assembly software component, constructed in accordance with the disclosed invention could handle a read request. In step 402, a read request is received. Contained within the read request will be information sufficient to determine which slice servers contain applicable data, as well as the minimum number of data slices that must be retrieved before the requested data can be reconstructed. Further information on one method that can be used to associate data requests with particular slice servers is contained in U.S. patent application Ser. No. 11/973,621, titled “VIRTUALIZED DATA STORAGE VAULTS ON A DISPERSED DATA STORAGE NETWORK,” filed on Oct. 9, 2007 assigned to Cleversafe, Inc, and hereby incorporated by reference in its entirety. In step 404, the variable m is initialized to the minimum number of slices required to construct the requested data. As described herein, for each successfully received and validated slice, m is decremented.

In step 406, a list of slice servers each holding one required data slice that has yet to be received is assembled, and in step 408, the list is ordered by any applicable criteria. Further information on criteria by which the list may be ordered is contained in U.S. patent application Ser. No. 11/973,622, titled “SMART ACCESS TO A DISPERSED DATA STORAGE NETWORK,” filed on Oct. 9, 2007, assigned to Cleversafe, Inc, and hereby incorporated by reference in its entirety. In step 410, read requests are issued to the first k slice servers on the assembled list, where k is at least equal to m, the minimum number of data slices needed to reconstruct the requested data segment, but could be as large as n, the number of data slices that have data relevant to the requested data segment. In step 412, r data slices are received, and in step 414 the number of received data slices r is subtracted from the variable m. Note that the number of received data slices r may be smaller than the number of requested data slices k. In step 416, m is compared to zero, and if m is not equal to zero, execution returns to step 406, and execution proceeds as normal from there. However, if m is equal to zero, a collection of data transformations may optionally be applied to the received slices in step 418. The applied data transformations can include decryption, decompression, and integrity checking. For example, each data slice may have a cyclical redundancy check (“CRC”), or other form of checksum appended to the data contained in the slice. This checksum could be compared against a checksum calculated against the received data to ensure that the data was not corrupted while it was stored or during the transmission process.

In step 420, it is determined if the applied data transformations were successful for all of the received data slices. If the applied data transformations were not successful for some of the received slices, m is incremented by this number in step 422, and execution is resumed at step 406. The data transformations could fail, for example, if an integrity check revealed that a received data slice may be been corrupted. However, if the applied data transformations were successful for all received data slices, the received slices are assembled into the requested block of data in step 424. The same or different data transformations may optionally be applied to the assembled data block in step 426, which completes the read process.

In FIGS. 5A-5B, the process by which an iSCSI Target, or other data dispersal/assembly software component, constructed in accordance with the disclosed invention could handle a write request is illustrated. In step 502 a write request is received. Included in this write request is a data segment to be written that could span many fixed length blocks. In addition, the write request will contain information sufficient to determine which slice servers the data segment should be written to, as well as information required by the information dispersal algorithm to slice each block, i.e., the number of slices to be written, referred to as n, as well as the minimum number of slices that are required to recover the data, referred to as m. Further information on one method that can be used to associate data writes with particular slice servers is contained in U.S. patent application Ser. No. 11/973,621, titled “VIRTUALIZED DATA STORAGE VAULTS ON A DISPERSED DATA STORAGE NETWORK,” filed on Oct. 9, 2007 and assigned to Cleversafe, Inc.

In step 504, the data segment is blocked into identical length fixed-size blocks. A number of data transformations may optionally be applied to each block in step 506, and an information dispersal algorithm is applied in step 508. In particular, the Cauchy Reed-Solomon dispersal algorithm could be applied to each block, resulting in a predetermined number of data slices. In step 510, a number of data transformations are optionally applied to each data slice.

In the disclosed system, writes are performed transactionally, meaning that all data slices must be successfully written before a write is deemed complete. In step 512, a write transaction is initiated to the data storage network. As discussed herein, all slice servers are simultaneously contacted, and in step 514, a confirmation that at least n receiving slice servers are prepared to begin the write transaction must be received, or the transaction is rolled back in step 516.

In step 518 blocks are grouped for transmission, and in step 520 data slices are transmitted to the slice servers that indicated their ability to receive and store slices. The number of slice servers that successfully received and stored their assigned data slices is checked in step 522, and if less than n slices are successfully stored, the transaction is rolled back in step 516. In step 524, a commit transaction is begun on all servers with successful writes. As illustrated by step 526, a check can be made to determine if a required number of services have committed. For example, if a threshold number of servers have responded to a commit command, then the commit transaction can be said to have completed successfully.If the commit transaction fails, an error is logged in step 528.

Detailed Description of the Improved File System Adapted for Use With a Dispersed Data Storage Network

In addition to the block based interface described above, a dispersed data storage network could also be accessed through a specially designed file interface. The file interface disclosed below is especially designed to access a dispersed data storage network (“DDSN”), and preserves the advantages of the disclosed block-based interface while providing a number of further advantages. The block based iSCSI interface is limited by the client initator in terms of number of concurrent requests, caching behavior and handling of multiple users (both readers and writers). The file interface does not face these restrictions and can potentially provide better performance and allow multiple usage. Additionally the same vault could be accessed from a variety of types of clients such as smart phones or applets as well as traditional desktop machines. Further, to aid in user adoption, the disclosed DDSN file interface could be provided as a virtual file system interface, and higher level interfaces to commonly used network file systems, such as NFS, CIFS, WebDAV and FTP could be provided. In such an implementation, a user would notice little or no difference when accessing the DDSN than when accessing a file stored on her local drive.

The disclosed File/Object implementation dispenses of the need for file system metadata, while still maintaining the flexibility that file system metadata grants. This is achieved through clean separation of the file system representation logic (as implemented by File/Object) and the file system storage, as implemented by a quantity of slice servers. In one embodiment, this separation allows two key assumptions to be made regarding the data format of information stored on the DDSN without concern for the efficiency or durability of that format.

First, as all stored data is associated with a file vault, it can be assumed that the data source identifier for the root object associated a particular file value is fixed across the entire vault. As a result, the file-object layer is not required to consult any on-disk reference to determine where a particular file system object resides or what other objects reference it.

Second, all data source identifiers are large randomly generated numbers, such as a Universally Unique Identifier, as opposed to monotonically increasing references used in traditional file systems. Traditional file systems use monotonically increasing references as they allow for near instantaneous lookup of data related to an identified file when combined with traditional lookup table structures. However, for a file system especially adapted for use with a dispersed data storage network, the use of a random identifier relieves the File-Object system from having to track allocated and free identifiers, which is typically achieved through the use of a “bookkeeping” bit mask. This allows for the flexible increase or decrease of space allocated to a particular vault at any time, as there are no assumptions about the allocation of size at the time that a vault is created.

One feature of the disclosed DDSN File System (“DFS”) is that it provides for the caching of directory objects and file system metadata. This provides a significant increase in performance and a significant decrease in network traffic; for instance, routine file system accesses do not require a directory object to be read from the DDSN multiple times, thereby allowing near instantaneous access after the directory is read the first time, and eliminating additional packets that would have resulted from reading the directory object from the DDSN multiple times. Depending on the implementation of the particular DDSN, a file system cache could reside on each client computer, or a grid access computer could maintain a file system cache for a plurality of client computers. Note that only file system objects, such as directory objects and file system metadata (i.e., metadata associated with directory objects and file objects), are cached; actual file data is not cached by the disclosed file system. Further note that file system metadata refers to data that describes a particular directory or file, such as the date and time that the referenced directory or file was last modified.

Another feature of the disclosed DFS is that all operations including create operations, read operations, update operations, and delete operations, are performed transactionally, meaning that every step of an operation is verified before it is deemed complete, and any failed operation is “rolled back.” For example, when an update operation for a particular data segment is performed, every updated data slice associated with the updated data segment must be written before the update transaction is deemed complete. Otherwise, the update transaction fails, and is rolled back, thereby preventing potential corruption of data stored on the DDSN.

In addition, while this application discusses DFS accesses in a unitary manner, accesses of multiple segments within a file could occur concurrently based on the capabilities of a particular grid client. For example, a powerful grid client with ample bandwidth and memory to store data could read or write multiple data segments in a single message and could utilize multiple threads or processes to perform such reads or writes. This would better utilize the network bandwidth and greatly increase performance in a high latency environment.

Returning to the Figures, and to FIG. 6 in particular, a distributed computer system implementing a DDSN 600 is depicted. The illustrated system includes a client/user computer 202, a grid access computer 220 and some number of slice servers 240,250,260. Within the client computer 202 an application program 204 accesses a networked file system 544, such as WebDAV, NFS, or some other networked file system. The networked file system 544 will issue commands to a network layer 212 operating on the client computer 548. Alternatively, a web browser 546 accessing a web page published by the grid access computer 220 may directly issue commands to the network layer 212.

The network layer 212 issues packets to the network 230 to carry out any received commands. File system commands will be routed to the grid access computer 220 where they will be processed by a network layer 224 operating thereon. Packets received by the network layer 224 may be passed to Server Layer 554, which, for file system related packets, will examine the packets and, based on the contents of the packets, issue commands to File-Object Layer 552. Server Layer 554 examines each packet passed to it by Network Layer 224 and, based on the requesting file system, e.g., NFS, WebDAV, etc., as well as the specific type of packet, will issue a command to the File-Object Layer 552. The File-Object Layer 552 presents a limited interface to the Server Layer 554, and effectively implements a virtual file system for nearly any type of networked file system for which an interface exists.

The File-Object Layer 552 issues commands to the Access Application 553, which implements an information dispersal algorithm in accordance with the received commands. For example, if a read command is received by the File-Object Layer 552, the Access Application 553 will issue network packets for transmission by Network Layer 224 to Slice Servers 240,250,260 to carry out the read.

FIG. 7 is a high-level flowchart illustrating how a file might be read using DFS. To start accessing DFS a grid access computer, client computer, or some other device seeking access to the DDSN through DFS could load a particular file vault associated with the desired DDSN in step 602. In step 604, the root directory object would be loaded from the DDSN. Steps 602 and 604 would generally be performed on initialization, and would not need to be performed again. On the first access of a particular file vault step 606 would be executed, and metadata associated with files and directories listed in the root directory would be loaded from the DDSN.

In step 608, intervening directory objects, meaning those between the desired file and the root directory of the vault, would be read, along with the metadata associated with the intervening directory objects in step 608. Once the home directory of the desired file has been opened, the file object metadata associated with the desired file is loaded in step 610, and the file object itself is loaded in step 612. The desired file may then be manipulated.

FIG. 8A illustrates the process by which a directory object may be loaded into the file system cache and accessed. In step 702 a request is made for a particular directory object. This request could come from an application level program directly accessing DFS or a higher level file system interface. In step 704, a check is made to determine whether the requested directory object is resident within the file system cache. If it is, execution resumes at step 710. However, if it is not, the directory object and associated metadata object are read from the DDSN in step 706, and both are populated into the file system cache in step 708 as shared read only cache objects, meaning that any program may access the directory object and associated metadata object, but neither may be modified. In step 710, the directory object is loaded from the cache and accessed by the calling program in step 712.

FIG. 8B illustrates the process by which a file object may be loaded into the file system cache and accessed. In step 721 a file object is requested. This request could also come for an application level program directly accessing DFS or a higher level file system interface. In step 722 a request is made for the metadata object associated with the desired file object. In step 724, a check is made to determine whether the requested metadata object is resident within the file system cache. If it is, execution resumes at step 730. However, If it is not, the metadata object is read from the DDS in step 726, and it is populated into the file system cache in step 728 as a shared read only cache object, meaning that any program may access the metadata object, but it may not be modified. In step 730, the metadata object is loaded from the cache and it is accessed by the calling program in step 732. In step 734, the requested file object may be accessed by the calling program through use of the file object identifier embedded within the metadata object.

FIG. 9 illustrates how a file or directory could be created within an already loaded shared read only directory object. In step 802, a request is made to create a new file or directory within an already loaded directory. In step 804, the already loaded base directory object is copied into an identical exclusive write directory object. Other programs may continue to read the already loaded directory object from the file system cache. In step 806, the new file object or directory object is created within the exclusive write directory object. In step 808, the shared read only base directory object is invalidated within the file system cache along with metadata objects associated with any directory objects or file objects referred to by the base directory object. In step 812 the exclusive write directory object is written to the DDSN and, on confirmation of a successful write, destroyed within the file system cache in step 814.

The procedure to create a virtual dispersed file on a DDSN is described in FIG. 10A. First in step 902 an object representing metadata for the newly created file is generated and initialized with the metadata values, such as, for example, creation time. Then in step 904 a new data object is created representing the content of the file. As the file is new the content is a zero length file object. In step 906, the two objects generated above are linked to each other by embedding the object id of the data object in the metadata object. In step 908 these two objects are encoded using an information dispersal algorithm, segmented, dispersed and stored on the DDSN. Then, in step 910, the newly created file object is added to the parent directory object, and the metadata object of the parent directory is modified to reflect the new size of the parent directory. In step 912, the modified directory object and metadata object of the parent directory are segmented, dispersed and stored on the DDSN. Finally, in step 914, the contents of the file are stored to DDSN.

The procedure to create a virtual dispersed directory on a DDSN is described in FIG. 10B. First in step 922 an object representing metadata for the newly created directory is generated and initialized with the metadata values, such as, for example, creation time. Then in step 924 a new data object is created representing the content of the directory. As the directory is new, it will be an empty list of files and directories contained within the directory. In step 926, the two objects generated above are linked to each other by embedding the object id of the directory object in the metadata object. In step 928, these two objects are segmented and dispersed using an information dispersal algorithm, and stored on the DDSN. Then, in step 930, the newly created directory object is added to the parent directory object, and the metadata object of the parent directory is modified to reflect the new size of the parent directory. Finally, in step 932, the modified directory object and metadata object of the parent directory are segmented, dispersed and stored on the DDSN.

Another feature of the disclosed file system is the ability to store variable sized data segments to a DDSN, as opposed to fixed sized blocks or segments. In particular, the disclosed file system segments a collection of data into one or more data segments. These data segments may be of the same size. Alternatively, a segmentation strategy may be employed whereby variable sized data segments are created. One strategy would be to use relatively small data segments near the beginning of a collection of data, and to increase the size of the data segments as data stored later within the collection of data was processed. This would allow for quicker access to data stored near the beginning of a collection of data with the offsetting disadvantage of increased network traffic due to additional requests to the DDSN.

The segmentation strategies described above would be particularly well suited for use when accessing a streaming media presentation. The smaller segment size used for the initial portions of the presentation would be accessed quickly, allowing the stream to start faster and a buffer of media content to be created. Later portions of the presentation would be accessed using larger segment sizes, thereby minimizing network traffic as the remainder of the presentation was viewed.

While segmenting a collection of data is generally desirable as segmentation enhances random access performance within a collection of data, certain collections of data, such as file system objects, file system metadata objects, and other collections of data are not of use unless the entire collection of data in question is available. In such a case, a flag may be associated with a collection of data indicating that the collection of data should not be segmented. This flag may be exported to a DFS user or the flag may be for use only by the DFS itself.

FIG. 11A shows the segmentation of a file, directory or other collection of data before it is stored on the DDSN. In step 1002, the data to be stored is evaluated on various criteria to determine the best segmentation strategy. This could include size, need for random access, type of access or client, or other criteria that could affect performance or storage. Based on these criteria, it is determined whether segmentation is desirable in step 1004. If segmentation is not desirable, such as, for example, for a metadata object, the collection of data is written to the DDSN as one segment in step 1010. However, if segmentation is desirable, the collection of data is segmented according to the selected segmentation strategy in step 1006. In step 1008, each data segment is written to the DDSN.

FIG. 11B shows the reconstitution of segmented data when it is retrieved from the DDSN. In step 1022, the segmentation information for the requested collection of data is retrieved, and a determination of whether or not the collection of data is segmented is made in step 1024. If the collection of data is not segmented, the entire collection is read in step 1026. However, if the collection of data is segmented, all of the segments are retrieved in accordance with the segmentation information in step 1028. In step 1030, the collection of data is reconstructed, and returned.

The foregoing description of the invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or to limit the invention to the precise form disclosed. The description was selected to best explain the principles of the invention and practical application of these principles to enable others skilled in the art to best utilize the invention in various embodiments and various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention not be limited by the specification, but be defined by the claims set forth below. 

1. A method for execution by a computer, the method comprising the steps of: receiving a request to access a data segment based on a file object identifier, wherein the data segment is encoded into a plurality of data slices that is dispersedly stored on a plurality of slice servers, wherein the data segment is reconstructable from a threshold number of the plurality of data slices; in response to the request, determining whether an object associated with the file object identifier is cached, wherein the object includes one or more directory objects and one or more associated metadata objects; when the object is not cached, requesting the object from at least some of the plurality of slice servers by: requesting a root directory object based on a file vault associated with the data segment, wherein the root directory object includes information that points to a root directory metadata object and information that points to the plurality of slice servers, an intervening directory object, or to a file directory object; when the root directory object includes the information that points to the plurality of slice servers, requesting the root directory metadata object; when the root directory object includes the information that points to the intervening directory object: requesting the intervening directory object based on the information that points to the intervening directory object, wherein the intervening directory object includes information that points to an intervening directory metadata object and information that points to another intervening directory object or to the file directory object; and requesting the intervening directory metadata object based on the information pointing to the intervening directory metadata object; when the file directory object is pointed to: requesting the file directory object based on the information that points to the file directory object, wherein the file directory object includes information that points to a file directory metadata object and information that points to the plurality of slice servers storing the data segment; and requesting the file directory metadata object based on the information pointing to the file directory metadata object; receiving object slices of the object from slice servers of the at least some of the slice servers, wherein the object is encoded into a plurality of object slices; when at least a threshold number of object slices is received, reconstructing the object from the at least the threshold number of object slices, wherein the threshold number of object slices is less than the plurality of object slices; caching the object to produce a cached object; and requesting access to the data segment from the plurality of slice servers based on the cached object.
 2. The method of claim 1, wherein the one or more directory objects comprises: a root directory object that includes information that points to a next directory object and includes information that points to a root directory metadata object; and a file directory object that includes identity of the plurality of slice servers and information that points to a file directory metadata object, wherein the one or more metadata objects includes the root directory metadata object and the file directory metadata object.
 3. The method of claim 2, wherein the object further comprises: at least one intervening directory object that includes information that points to another next directory object and information that points to an intervening directory metadata object.
 4. The method of claim 1 further comprises at least one of: in response to requesting the root directory object: receiving root directory slices from slice servers of the at least some of the slice servers; when a threshold number of root directory slices is received, reconstructing the root directory object from the threshold number of root directory slices; and caching the root directory object to produce a cached root directory object; in response to requesting the root directory metadata object: receiving root directory metadata slices from slice servers of the at least some of the slice servers; when a threshold number of root directory metadata slices is received, reconstructing the root directory metadata object from the threshold number of root directory slices; and caching the root directory metadata object to produce a cached root directory metadata object; in response to requesting the intervening directory object: receiving intervening directory slices from slice servers of the at least some of the slice servers; when a threshold number of intervening directory slices is received, reconstructing the intervening directory object from the threshold number of intervening directory slices; and caching the intervening directory object to produce a cached intervening directory object; in response to requesting the intervening directory metadata object: receiving intervening directory metadata slices from slice servers of the at least some of the slice servers; when a threshold number of intervening directory metadata slices is received, reconstructing the intervening directory metadata object from the threshold number of intervening directory slices; and caching the intervening directory metadata object to produce a cached intervening directory metadata object; in response to requesting the file directory object: receiving file directory slices from slice servers of the at least some of the slice servers; when a threshold number of file directory slices is received, reconstructing the file directory object from the threshold number of file directory slices; and caching the file directory object to produce a cached file directory object; and in response to requesting the file directory metadata object: receiving file directory metadata slices from slice servers of the at least some of the slice servers; when a threshold number of file directory metadata slices is received, reconstructing the file directory metadata object from the threshold number of file directory slices; and caching the file directory metadata object to produce a cached file director metadata object.
 5. The method of claim 1, wherein the requesting the data segment from the plurality of slice servers further comprises: accessing the cached object to obtain the identity of the plurality of slice servers storing the data segment; and requesting access to a data slice from each of at least a threshold number of the plurality of slice servers.
 6. The method of claim 1, wherein the requesting access to the data segment further comprises at least one of: requesting read access to the data segment; and requesting write access to the data segment.
 7. The method of claim 1 further comprises: when the reconstructing the object is unsuccessful, rolling back access to the data segment to a previously successful data segment access.
 8. A computer comprises: a network port for communicating with a network; and a central processing unit operable to: receive a request to access a data segment based on a file object identifier, wherein the data segment is encoded into a plurality of data slices that is dispersedly stored on a plurality of slice servers, wherein the data segment is reconstructable from a threshold number of the plurality of data slices and wherein the threshold number of data slices is less than the plurality of data slices; in response to the request, determine whether an object associated with the file object identifier is cached, wherein the object includes one or more directory objects and one or more associated metadata objects; when the object is not cached, request the object from at least some of the plurality of slice servers by: requesting a root directory object based on a file vault associated with the data segment, wherein the root directory object includes information that points to a root directory metadata object and information that points to the plurality of slice servers, an intervening directory object, or to a file directory object; when the root directory object includes the information that points to the plurality of slice servers, requesting the root directory metadata object; when the root directory object includes the information that points to the intervening directory object: requesting the intervening directory object based on the information that points to the intervening directory object, wherein the intervening directory object includes information that points to an intervening directory metadata object and information that points to another intervening directory object or to the file directory object; and requesting the intervening directory metadata object based on the information pointing to the intervening directory metadata object; when the file directory object is pointed to: requesting the file directory object based on the information that points to the file directory object, wherein the file directory object includes information that points to a file directory metadata object and information that points to the plurality of slice servers storing the data segment; and requesting the file directory metadata object based on the information pointing to the file directory metadata object; receive object slices of the object from slice servers of the at least some of the slice servers, wherein the object is encoded into a plurality of object slices; when at least a threshold number of object slices is received, reconstruct the object from the at least the threshold number of object slices, wherein the threshold number of object slices is less than the plurality of object slices; cache the object to produce a cached object; and request access to the data segment from the plurality of slice servers based on the cached object.
 9. The computer of claim 8, wherein the one or more directory objects comprises at least one of: a root directory object that includes information that points to a next directory object and includes information that points to a root directory metadata object; at least one intervening directory object that includes information that points to another next directory object and information that points to an intervening directory metadata object; and a file directory object that includes identity of the plurality of slice servers and information that points to a file directory metadata object, wherein the one or more metadata objects includes the root directory metadata object and the file directory metadata object.
 10. The computer of claim 8, wherein the central processing unit is further operable to perform at least one of: in response to requesting the root directory object: receive root directory slices from slice servers of the at least some of the slice servers; when a threshold number of root directory slices is received, reconstruct the root directory object from the threshold number of root directory slices; and cache the root directory object to produce a cached root directory object; in response to requesting the root directory metadata object: receive root directory metadata slices from slice servers of the at least some of the slice servers; when a threshold number of root directory metadata slices is received, reconstruct the root directory metadata object from the threshold number of root directory slices; and cache the root directory metadata object to produce a cached root directory metadata object; in response to requesting the intervening directory object: receive intervening directory slices from slice servers of the at least some of the slice servers; when a threshold number of intervening directory slices is received, reconstruct the intervening directory object from the threshold number of intervening directory slices; and cache the intervening directory object to produce a cached intervening directory object; in response to requesting the intervening directory metadata object: receive intervening directory metadata slices from slice servers of the at least some of the slice servers; when a threshold number of intervening directory metadata slices is received, reconstruct the intervening directory metadata object from the threshold number of intervening directory slices; and cache the intervening directory metadata object to produce a cached intervening directory metadata object; in response to requesting the file directory object: receive file directory slices from slice servers of the at least some of the slice servers; when a threshold number of file directory slices is received, reconstruct the file directory object from the threshold number of file directory slices; and cache the file directory object to produce a cached file directory object; and in response to requesting the file directory metadata object: receive file directory metadata slices from slice servers of the at least some of the slice servers; when a threshold number of file directory metadata slices is received, reconstruct the file directory metadata object from the threshold number of file directory slices; and cache the file directory metadata object to produce a cached file directory metadata object.
 11. The computer of claim 8, wherein the central processing unit is further operable to request the data segment from the plurality of slice servers further by: accessing the cached object to obtain the identity of the plurality of slice servers storing the data segment; and requesting access to a data slice from each of at least a threshold number of the plurality of slice servers.
 12. The computer of claim 8, wherein the central processing unit is further operable to request access to the data segment further by at least one of: requesting read access to the data segment; and requesting write access to the data segment.
 13. The computer of claim 8, wherein the central processing unit is further operable to: when the reconstructing the object is unsuccessful, roll back access to the data segment to a previously successful data segment access. 